Skip to content

feat(stream): add max_stream_resolution option to cap encode resolution - #5512

Open
martona wants to merge 4 commits into
LizardByte:masterfrom
martona:feature/max-stream-resolution
Open

feat(stream): add max_stream_resolution option to cap encode resolution#5512
martona wants to merge 4 commits into
LizardByte:masterfrom
martona:feature/max-stream-resolution

Conversation

@martona

@martona martona commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Description

New config option (max_stream_resolution = 2560x1440): client resolution requests exceeding the cap are downscaled preserving aspect ratio (even-aligned). Applied both to the RTSP viewport (encode size) and the launch session, so display-device configuration switches the host display to the actual streamed size.

Encoder latency scales with pixel count. Moonlight's resolution setting is global across hosts, so a single slow-encoder host forces a fleet-wide compromise; this makes the tradeoff per-host instead. Measured example: a host whose 4K HEVC encode adds ~120ms of processing latency drops to ~35ms capped at 1440p, with the client settings untouched.

Includes web UI (Audio/Video -> "Maximum Stream Resolution"), docs, and locale entries; config consistency tests pass.

Screenshot

image

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

See our AI usage policy.

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

martona and others added 4 commits August 15, 2026 21:14
Add a host-side cap on the streamed video resolution. Client requests
exceeding the cap are downscaled preserving aspect ratio, with even
dimensions.

The cap is applied both to the RTSP viewport (encode size) and to the
launch session (so display device configuration switches the host
display to the actual streamed size rather than the uncapped request).
The option was registered in the config options map but had no input
markup in the tab component, so it never appeared in the web UI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KPZiLfh6KcTYcUtnydjZfC
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant